Skip to content

controller: unlabel nodes when pool is deleted - #140

Open
cheesesashimi wants to merge 1 commit into
bootc-dev:mainfrom
cheesesashimi:zzlotnik/fix-node-unlabelling
Open

controller: unlabel nodes when pool is deleted#140
cheesesashimi wants to merge 1 commit into
bootc-dev:mainfrom
cheesesashimi:zzlotnik/fix-node-unlabelling

Conversation

@cheesesashimi

Copy link
Copy Markdown

Whenever a BootcNodePool is deleted, the nodes which belong to that pool were still being managed because the labels were not removed from the nodes which belong to that pool. This meant that the daemon continued to run on those nodes. Adding a finalizer to the pool blocks deletion until all of the nodes which belong to that pool have been unlabeled.

This fixes #138

@cheesesashimi
cheesesashimi force-pushed the zzlotnik/fix-node-unlabelling branch 2 times, most recently from 2490e20 to 3b61e84 Compare August 13, 2026 17:08
@alicefr

alicefr commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

@cheesesashimi thanks, it looks great!

Whenever a BootcNodePool is deleted, the nodes which belong to that pool
were still being managed because the labels were not removed from the
nodes which belong to that pool. This meant that the daemon continued to
run on those nodes. Adding a finalizer to the pool blocks deletion
until all of the nodes which belong to that pool have been unlabeled.

Assisted-by: AI
Signed-off-by: Zack Zlotnik <zzlotnik@redhat.com>
@cheesesashimi
cheesesashimi force-pushed the zzlotnik/fix-node-unlabelling branch from 3b61e84 to c60920c Compare August 14, 2026 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Nodes belonging to a BootcNodePool should not be managed if the pool is deleted

2 participants